Posts tagged “bug reports”

Dictation is faster for long reproduction steps but wrong for exact values. Here is when to talk through a bug, when to type it, and how to handle Firefox.

How to place numbered pins on a single screenshot so a developer reads your bug report as an ordered checklist, not a scavenger hunt.

Teams switching from Jam.dev to a link-based review make the same handful of errors. Here is what stalls triage and how to correct each one.

Vague selectors, no screenshot, five bugs in one message: the patterns that make Bolt guess wrong, and the concrete fix for each.

Walk through capturing a Lovable preview, pinning the exact spot, and pasting the markdown into the chat so the fix lands on the first try.

An agent will happily edit the wrong element if your markdown bug report is vague. Here are the specific mistakes that cause it and the concrete fix for each.

A worked example: the same bug report shown as a published review link for people and as clean markdown for Cline to read and fix.

The Replit Agent built the screen, the preview is broken, and you need to say exactly what and where. Here is the capture-comment-return loop, step by step.

A pinned screenshot and one dictated sentence beat a paragraph of description when you prompt Windsurf. Here is the step-by-step flow.

Go from a broken screen to a markdown link Aider can read in about two minutes. Here is the exact sequence, step by step.

Claude Code will happily act on bad input. Here are five specific ways UI feedback goes wrong before it reaches the agent, and what to send instead.

The precise vocabulary for bug reports a coding agent can fix without follow-up questions. Each term defined, with practical notes on when it matters.